Resource Management Unit for Capturing Operating System Configuration States and Memory Management

ABSTRACT

This disclosure describes methods, devices, systems, and procedures in a computing system for capturing a configuration state of an operating system executing on a central processing unit (CPU), and offloading memory management tasks, based on the configuration state, to a resource management unit such as a system-on-a-chip (SoC). The resource management unit identifies a status of a resource requiring memory swapping based on the captured configuration state of the operating system. The resource management unit then swaps the memory to alleviate the CPU from processing the swap thereby improving overall computing system performance.

RELATED APPLICATION

This application is a continuation application of InternationalApplication No. PCT/US2019/067560, filed Dec. 19, 2019 and titled“Resource Management Unit for Capturing Operating System ConfigurationStates and Memory Management”, the disclosure of which is incorporatedin its entirety by reference herein.

BACKGROUND

Computer systems generally include a central processing unit (CPU),memory, input/output (I/O) devices, and other electronic components, aswell as software, firmware, and data. Operating system (OS) softwarestored in memory and executed on the CPU manages the computer system'score functions, such as scheduling tasks, executing softwareapplications, managing memory, and controlling I/O and peripheraldevices. Additional hardware or other integrated circuit components,such as a memory management unit (MMU), may be included on a motherboardto offload processing tasks from the CPU in effort to improveperformance of the system. These efforts to improve performance of thesystem with additional hardware or other components, however, often failto effectively or sufficiently improve system performance.

SUMMARY

This document describes an example computing system and method thatleverages a resource management unit for offloading memory managementtasks from a central processing unit (CPU). The resource management unitcaptures a configuration state of an operating system (OS) executing onthe CPU, identifies opportunities for memory management, and then, basedon the captured configuration state and the identified opportunities,offloads memory swapping tasks from the CPU to the resource managementunit.

The computing system includes the CPU, the resource management unit, andmemory having instructions that, responsive to execution by the CPU orthe resource management unit, cause the resource management unit tocapture the configuration state of the operating system, identify theopportunity for memory management, and execute a memory swap. In otheraspects, the computing system includes a hypervisor or virtual machine,and the resource management unit captures the configuration state of theoperating system of the hypervisor or virtual machine, identifies anopportunity for memory management, and executes a memory swap. Inadditional aspects, the resource management unit may swap using avariant size of the content in the memory without a set page-size (e.g.,block-size) limitation.

The details of one or more methods, devices, systems, and procedures forcapturing operating system configuration states with a resourcemanagement unit for identifying memory management opportunities andexecuting memory swapping tasks are set forth in the accompanyingdrawings and the following description. Other features and advantageswill be apparent from the description, drawings, and claims. Thissummary is provided to introduce subject matter that is furtherdescribed in the detailed description and drawings. Accordingly, thissummary should not be considered to limit the scope of the claimedsubject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

The details of one or more aspects of a resource management unit forcapturing operating system configuration states and memory managementare described with reference to the following drawings. The use of thesame reference numbers in different instances in the description and thefigures may indicate like elements.

FIG. 1 is a block diagram illustrating an example computing systemconfigured to capture operating system configuration states foroffloading tasks to a resource management unit (e.g., scaling clockrates, memory management, processing, managing vulnerabilities).

FIG. 2 is a block diagram illustrating another example computing system,including a hypervisor and virtual machine, configured to captureoperating system configuration states for offloading tasks to a resourcemanagement unit.

FIG. 3 illustrates an example device diagram for a user equipment thatcan implement various aspects of capturing operating systemconfiguration states for offloading tasks to a resource management unit.

FIG. 4 illustrates an example method for capturing operating systemconfiguration states for offloading tasks to a resource management unitin a computing system.

FIG. 5 illustrates an example method with additional detail forcapturing operating system configuration states for offloading tasks toa resource management unit in a computing system.

FIG. 6 is a block diagram illustrating an example computing systemdepicting an example operating system configuration state as captured bya resource management unit for offloading operating system tasks to theresource management unit.

FIG. 7 is a block diagram illustrating an example computing systemconfigured for capturing operating system configuration states by aresource management unit for dynamically scaling clock rates.

FIG. 8 illustrates an example method for capturing operating systemconfiguration states by a resource management unit in a computing systemfor dynamically scaling clock rates.

FIG. 9 is a block diagram illustrating an example computing systemconfigured for capturing operating system configuration states by aresource management unit for performing memory management tasks.

FIG. 10 illustrates an example method for capturing operating systemconfiguration states by a resource management unit in a computing systemfor managing memory swapping.

FIG. 11 is a block diagram illustrating an example computing systemconfigured for capturing operating system configuration states by aresource management unit for detecting and managing malware and softwarevulnerabilities.

FIG. 12 illustrates an example method for capturing operating systemconfiguration states by a resource management unit in a computing systemfor detecting and managing malware and software vulnerabilities.

DETAILED DESCRIPTION

This disclosure describes methods and systems for capturing operatingsystem configuration states to offload memory management tasks to aresource management unit. A computing system leverages a resourcemanagement unit, such as a system-on-a-chip (SoC), to capture aconfiguration state of an operating system (OS) executing on a centralprocessing unit (CPU) of the computing system. Based on theconfiguration state of the operating system, the resource managementunit identifies a status of a process resource in the computing systemrequiring memory management. The resource management unit then executesthe memory management, such as a memory swapping, to alleviate the CPUfrom processing the task, thus improving overall computing systemperformance. Given the resource management unit's view of the operatingsystem configuration state and resources, the resource management unitmay swap using a variant size of the content in the memory without a setpage-size (e.g., block-size) limitation.

This disclosure generally describes capturing an operating systemconfiguration state with a resource management unit and, based on thecaptured state, offloading tasks. Various ways in which to offload tasksare described, including processing tasks, memory management, malwareand vulnerability management, and dynamically scaling clock rates. Whilethese examples are described in subsections below, these subsections arenot intended to limit these examples to being only described in thosesubsections, their coexistence with other examples, or their independentoperation.

Capturing Operating System Configuration States and Offloading Tasks toa Resource Management Unit

Hardware components of a computer system are often configured to assistan operating system or CPU with processing tasks. These processingtasks, however, remain managed by the operating system, which isexecuted through the CPU. Further, these components impose their ownlimitations on the operating system and CPU, such as applicationprogramming interfaces (APIs) in the form of cyclic buffers, memorymapped input/output (MMIO), shared-memory limitations, and sizingrestrictions for swapping memory pages or I/O blocks. These limitationscontinue to burden the CPU, often causing delay or reduced performanceof the computing system, even from a user's perspective. For example, asthe operating system manages the system's resources, such as schedulingtasks, pausing execution of a process, allocating memory, swappingmemory, starting execution of another process, and so forth, a user'sinput or expected output in response to that input may be delayed. Thismay occur even if some of these functions are assigned to, and completedwith the help of, additional hardware because the operating systemremains responsible for assigning the tasks or executing certainfunctions related to these hardware components through the CPU, thusburdening the CPU.

In contrast, the resource management unit of this disclosure avoidsthese limitations by capturing the operating system configuration state,storing it into a database (e.g., memory) associated with or accessibleby the resource management unit, identifying from the database a statusof resources in the system, and independently processing tasksassociated with the resources. This independent processing by theresource management unit effectively alleviates the processor fromhaving to perform the tasks thus improving overall system performance.

Although the described resource management unit can be an SoC, otherhardware configurations may similarly be used, either alone or incombination with firmware or software that provides comparablefunctionality to the resource management unit of this disclosure.

FIG. 1 is a block diagram illustrating an example computing system 100having a resource management unit 102, e.g., a system-on-a-chip (SoC)and associated memory 104, as well as a processor 106 (e.g., the CPU)and its associated memory 108. The memory 104 and 108 arecomputer-readable storage media, and can include various implementationsof random-access memory (RAM), read-only memory (ROM), flash memory,cache memory, and other types of storage memory in various memory deviceconfigurations, including a shared memory configuration. The memory 108includes the operating system 110 and instructions that execute on theprocessor 106.

The resource management unit 102 includes an OS configuration statemanager 112 configured to capture or obtain (used interchangeablyherein) an OS configuration state 114 of the operating system 110. TheOS configuration state 114 reflects a momentary state or status of theoperating system at a given point in time. As an example, and forsimplicity of this discussion, the OS configuration state 114 reflects astatus of the operating system upon a resource transaction event 132occurring in the operating system 110. However, other events or timesmay similarly be selected to capture the OS configuration state.

The OS configuration state manager 112 captures and stores the OSconfiguration state 114 into an OS configuration state database(database) 116. The database 116 may be located in the memory 104 or anyother fast memory associated with the resource management unit 102,either fabricated on or as part of the resource management unit orlocated elsewhere in the computing system 100 and accessible by theresource management unit 102 via low-latency access. The OSconfiguration state database 116 may be any standard database structure,such as a table, tree, hierarchical, relational (e.g., MySQL, SQLite,Oracle, Sybase), NoSQL or object-oriented scheme, configured to captureindicators of the operating system configuration state as described inthis disclosure.

The OS configuration state 114 captured into the OS configuration statedatabase 116 may include information associated with a process runqueue, a process wait queue, active devices, and virtual memory tables.These queues include process data relevant to specific processes in eachqueue. The process data includes data defining the status of thatprocess as stored in a data structure, such as a process control blockor similar structure, as described further below for defining andtracking processes and activity in operating systems. The virtual memorytables define the storage allocation scheme in which a secondary storage124 (e.g., memory) can be addressed as though it were part of the memory108. Other example aspects of the operating system captured may includeprocess priority data, process run-time remaining, resource schedulingdata, resource usage data, memory usage data, memory mapping data,storage management data, active device data, a hypervisor status, avirtual machine (VM) status, a VM guest operating system status, orresources used by the hypervisor or virtual machine. Additionaloperating system aspects captured may be similar to those identifiedusing an operating system analysis tool, such as a Linux operatingsystem event-oriented observability tool, e.g., “perf.” This allows fortracking performance counters, events, trace points, tasks, workload,control-flow, cache misses, page faults, and other profiling aspects ofthe operating system to provide a robust reference perspective of theoperating system configuration state.

For purposes of this disclosure, a process is an instance of a program(e.g., binary program file) in execution on a processor 106 (or a coreor cores of the processor). A process may be defined by how it isreferenced in memory. Examples of a process definition in memory mayinclude elements of text (e.g., compiled program code), data (e.g.,global and static variables), heap (e.g., for dynamic memoryallocation), stack (e.g., local variables), and information related toprogram counters and registers. A state of a process (process state) inthe operating system may include: (i) a new process being created, (ii)a ready process that has its resources ready but not yet running on theprocessor, (iii) a running process that is being executed by theprocessor, (iv) a waiting process that is not running but is waiting foran event to occur or resource to become available, and (v) a terminatedprocess that has completed execution on the processor. Additionally, foreach process there is a data structure, referenced as a process controlblock in this disclosure (e.g., see FIG. 6), that stores theprocess-specific information. The process control block may include dataindicative of: (i) the process identification (ID), (ii) the processstate, (iii) processor registers and program counter (e.g., for swappingthe process in and out of the processor), (iv) processor schedulinginformation (e.g., priority information), (v) memory management data(e.g., page tables), (vi) accounting data (e.g., processor timeconsumed, limits), and (vii) input/output status data (e.g., devicesused, open files).

The resource management unit 102 further includes a resource statusmanager 118 and a resource task manager 120. The resource status manager118 identifies a status of a resource in the computing system, as storedin the database 116, based on the OS configuration state 114. Forexample, a status of a process is detected by referencing the processcontrol block of that process, thereby detecting the process state,registers, scheduling, priority, memory management, and otherprocess-related information. The resource task manager 120 processes atask associated with the status of the resource, as identified by theresource status manager 118, to alleviate the processor 106 fromperforming the task and thereby improving overall performance of thecomputing system 100. For example, if the process control blockindicates a process is in a waiting state and a memory resource isneeded, the resource task manager 120 processes a task of freeing memoryso the process may move from the wait state to the ready state forexecution. Although the OS configuration state manager 112, resourcestatus manager 118, and resource task manager 120 are shown in thediagram as being stored as executable instructions (e.g., firmware orsoftware) in the memory 104, the same may alternatively be formed indigital logic hardware blocks on the resource management unit 102, orenabled using a combination of firmware, software, and hardware blocks.

A communication manager 122 enables communications external to thecomputing system 100, such as to a networked computing environment, theInternet, or a cloud or multi-cloud network computing environment,generally referred to herein as a network 126. The resource managementunit 102 and processor 106 together form a processor complex in thecomputing system 100, and the memory 104, 108 include data orinstructions stored thereon to cause the processor complex 102, 106 toperform the methods and functions described throughout this document.

A secondary storage 124 provides additional storage (e.g., memory)functionality for the computing system 100. Examples of the secondarystorage 124 include non-volatile memory, fixed and removable mediadevices, and any suitable memory device or electronic data storage thatmaintains executable instructions and/or supporting data. The secondarystorage 124 can include various implementations of RAM, ROM, or othertypes of non-volatile memory such as a solid-state drive (SSD) or a harddisk drive (HDD), or combinations thereof. The secondary storage 124 maybe used for storing software applications or data, or for memorymanagement purposes.

The resource management unit 102 may include other components not shownin this example, such as processing units (e.g., central processingunits, graphics processing units, artificial intelligence processingunits, display processors, video processors), communication units (e.g.,modems), input/output controllers, and sensor hubs (see FIG. 3 foradditional examples).

The resource management unit 102 and the processor 106 communicate usinglow-latency communication and write transactions, either by way of theresource management unit being implemented on a same integrated circuitdie as the processor and its memory 108, or by using a high-speedinterface bus 128 and data link 130. The high-speed bus 128 may be anyfast bus standard that creates a seamless interface between the resourcemanagement unit 102 and the processor 106, such as the PeripheralComponent Interconnect Express bus, otherwise known as PCI Express orPCIe, or other similar open or proprietary bus standard with low-latencyperformance. The resource management unit 102 may also have a directmemory access (DMA) channel to the memory 108 via the data link 130 fortransferring data to/from the memory 108 without passing it through theprocessor 106.

In one example, capturing an OS configuration state 114 of the operatingsystem 110, in coordination with the OS configuration state manager 112on the resource management unit 102, includes detecting resourcetransaction events 132 indicative of operational status information ofthe operating system and its managed resources. Examples of resourcetransaction events include events regarding a process run queue, aprocess wait queue, process priority data, process run-time remaining,resource scheduling data, resource usage data, active device data,memory usage data, memory mapping data, virtual memory tables, storagemanagement data, a hypervisor status, a virtual machine (VM) status, aVM guest operating system, or resources used by the hypervisor orvirtual machine.

In one example, a resource transaction event 132 is detected and the OSconfiguration state 114 is captured by using an OS abstraction layer ofinstructions 134. These instructions 134 are executed by the processor106 to push the OS configuration state to the resource management unit102. Alternatively, or in combination with the abstraction layer, the OSconfiguration state manager 112 on the resource management unit 102 isconfigured to capture or pull the OS configuration state 114 upondetecting resource transaction events 132. In some cases these resourcetransaction events 132 are detected through monitoring writetransactions to the high-speed bus 128 interface and data link 130, suchas through API queues and interrupt lines.

The OS configuration state 114, captured via the OS configuration statemanager 112 in the resource management unit 102, is stored in the OSconfiguration state database 116 associated with the resource managementunit memory 104 so that the resource status manager 118 may identify astatus of any particular resource by accessing the database. Examples ofresources for which a status may be identified include a process runqueue, process wait queue, process priority data, process run-timeremaining, resource scheduling data, active device data, memory usagedata, memory mapping data, virtual memory tables, storage managementdata, a hypervisor, a virtual machine (VM), a VM guest operating system,and resources used by the hypervisor or virtual machine.

Based on an understanding of the OS configuration state database 116 andits depiction of operating system resources, the resource managementunit resource task manager 120 processes a task associated with thestatus of a resource. The resource management unit 102 identifies andacts on a resource task in advance of what the processor 106 mayidentify and process. The resource management unit can increaseprocessing priority or performance factors for a specific task, oraddress a security aspect of the computing system relative to aparticular process, or process an overhead management activity of thecomputing system. All these aspects can result in improved overallsystem performance and also an improved user's perception of responsiveprocessing. This reduced latency, both real and as perceived by a user,is enabled because the processor 106 can focus on user-perceivableactivities or other priorities while the resource management unitperforms overhead system management work and other processing tasks.

FIG. 2 is a block diagram illustrating another example of a computingsystem 100 generally including the resource management unit 102,operating system 110, memory 108, and processor 106. However, in thisexample the computing system 100 is configured with a hypervisor 136 andvirtual machine 138 running a guest operating system. Although only onevirtual machine is depicted, the computing system 100 may includemultiple virtual machines and/or guest operating systems as managed bythe hypervisor 136.

The components, functionality, and methods previously discussed withrespect to FIG. 1 perform similarly for managing the hypervisor andvirtual machine components included in FIG. 2. For example, the OSconfiguration state manager 112 of the resource management unit 102stores the OS configuration state 114 into an OS configuration statedatabase 116. The OS configuration state 114, however, may includeoperating system aspects relating to the hypervisor 136 and virtualmachine 138. The resource status manager 118 again identifies a statusof a resource in the computing system, as stored in the database 116based on the configuration state 114 of the operating system 110,hypervisor 136, and virtual machine 138. The resource task manager 120processes a task associated with the status of the resource, asidentified by the resource status manager 118, to alleviate theprocessor 106 from performing the task, thus improving overallperformance of the computing system.

Similar to the aspects discussed in reference to FIG. 1, capturing theOS configuration state 114 of the operating system 110, the hypervisor136, and the virtual machine 138, includes obtaining operational statusinformation of the operating system and its managed resources. Thisinformation may be obtained by monitoring and detecting the OS resourcetransaction events 132. Such information may be captured by the resourcemanagement unit 102 by using virtualization technologies 140, such assingle root input/output virtualization (SR-IOV) or multi-rootinput/output virtualization (MR-IOV), to allow isolation of the bus(e.g., PCIe) by the hypervisor or virtual machine for manageability andperformance. Example operational status information of the managedresources may relate to a process run queue, a process wait queue,process priority data, process run-time remaining, resource schedulingdata, resource usage data, active device data, memory usage data, memorymapping data, virtual memory tables, storage management data, ahypervisor, a virtual machine, a virtual machine guest operating system,or resources used by the hypervisor or virtual machine.

FIG. 3 is a conceptual diagram illustrating an example computing system300 as, or integrated into, a computing device 302 configured withcomponents and functionality for capturing OS configuration states foroffloading tasks to a resource management unit (e.g., a resourcemanagement unit 102). The computing device 302 is an example computingenvironment or application for the computing system 100 of FIG. 1. Assome non-limiting examples, the computing device 302 may be a mobilephone 302-1, a tablet device 302-2, a laptop computer 302-3, atelevision/display or desktop or server computer 302-4, a computerizedwatch 302-5, or other wearable device 302-6, a game controller 302-7, anetworked multimedia or voice assistant system 302-8, or an appliance302-9.

The computing device 302 includes the resource management unit 102, thememory 104, and the OS configuration state manager 112 configured tocapture or obtain the OS configuration state 114 of the operating system110 stored in the memory 108 and executing on the processor 106. The OSconfiguration state manager 112 of the resource management unit 102stores the OS configuration state 114 into an OS configuration statedatabase 116 associated with the resource management unit 102. Theresource status manager 118 identifies a status of a resource in thecomputing device, as stored in the database 116 based on the OSconfiguration state 114. The resource task manager 120 processes a taskassociated with the status of the resource, as identified by theresource status manager 118, to alleviate the processor 106 fromperforming the task and thereby improving overall performance of thecomputing device.

The computing device 302 also includes communication components 304,input/output components 306, communication interfaces 310, andinput/output interfaces 312. These interfaces and components mayleverage the memory 108 and processor 106, and/or be incorporated intothe resource management unit 102 to leverage its operations.

The resource management unit 102 may also include processing units 308.The processing units 308 process computer-executable instructions toperform operations and execute functions of the computing device 302.The processing units 308 may include any combination of controllers,microcontrollers, processors, microprocessors, hardware processors,hardware processing units, digital-signal-processors, graphicsprocessors, graphics processing units, video processors, videoprocessing units, and the like.

The memory 104 associated with the resource management unit 102, and thememory 108, store information and instructions that are executed by theprocessor 106 and/or processing units 308 to perform operations andexecute functions. These memories are configured to provide thecomputing device 302 with persistent and/or non-persistent storage ofexecutable instructions (e.g., firmware, recovery firmware, software,applications, modules, programs, functions, and the like) and data(e.g., user data, operational data, scan results) to support executionof the executable instructions. Examples of these memories includevolatile memory and non-volatile memory, fixed and removable mediadevices, and any suitable memory device or electronic data storage thatmaintains executable instructions and supporting data. These memoriescan include various implementations of RAM, ROM, flash memory, cachememory, and other types of storage memory in various memory deviceconfigurations, or may be a solid-state drive (SSD), a hard disk drive(HDD), or combination thereof. These memories exclude propagatingsignals.

The communication components 304 enable wired and/or wirelesscommunication of device data between the computing device 302 and otherdevices, computing systems, and network 126. The communicationcomponents 304 can include receivers, transmitters, and transceivers forvarious types of wired and wireless communications. Communicationinterfaces 310 handle messaging and protocols associated withcommunications being transmitted and received using the communicationcomponents 304.

The input/output components 306 provide connectivity to the computingdevice 302. For example, the input/output components 306 may include auser interface device that manages a user interface of the computingdevice 302, or may provide additional connectivity, beyond just the userinterface device. The input/output components 306 can also include datainterfaces or data input ports for receiving data, including userinputs. The processor 106 and/or processing units 308 may tailoroperations according to input information obtained by the input/outputinterfaces 312 from the input/output components 306. Likewise, based oninformation obtained by the communication interfaces 310 from thecommunication components 304, the processor 106 and/or processing units308 tailor operations according to incoming or outgoing communications.

FIGS. 4-5 are flow diagrams 400, 500 illustrating high-level operationsof example methods for capturing operating system configuration statesin a computing system for offloading tasks to a resource managementunit. The operations of methods 400, 500, and other methods describedherein, may be embodied as programming instructions stored on anon-transitory, machine-readable (e.g., computer/processor-readable)medium, such as a RAM or ROM memory or other storage device forexecution in a computing device or devices, or may be performed byhardware blocks, or combinations thereof. In some examples, implementingthe operations of the methods can be achieved by a processor complex,including a main processor and a resource management unit, reading andexecuting the programming instructions stored in the memory, and/orfunctioning in combination with hardware blocks of the resourcemanagement unit. In some examples, implementing the operations of themethods can be achieved using a resource management unit such as asystem-on-chip (SoC), and/or other hardware components either alone orin combination with programming instructions executable by a processoror processors in a computing device.

The example methods described in this disclosure may include more thanone implementation, and different implementations of the methods may notemploy every operation presented in the respective flow diagrams, or mayemploy additional operations not shown. Therefore, while the operationsof the methods are presented in a particular order within the flowdiagram(s), the order of their presentations is not intended to be alimitation as to the order in which the operations may actually beimplemented, or as to whether all of the operations may be implemented.For example, one implementation of the methods might be achieved throughthe performance of a number of initial operations, without performingsubsequent operations, while another implementation of the methods mightbe achieved through the performance of all of the operations.

Referring now to example method 400 of FIG. 4, a first operation 402includes posting an operating system resource transaction event in amemory of a computing system responsive to the operating systemexecuting on a processor in the computing system. An operating systemtransaction event is indicative of when a configuration state of theoperating system may be captured because an operating system event isoccurring or has occurred. Capturing a configuration state of theoperating system includes obtaining operational status information ofthe operating system and its managed resources. Examples of suchresources and operating system operational status information include aprocess run queue, a process wait queue, process priority data, processrun-time remaining, resource scheduling data, resource usage data,active device data, memory usage data, memory mapping data, virtualmemory tables, storage management data, hypervisor activity, virtualmachine activity, virtual machine guest operating system activity, andother related process and system activities, statuses, and data.

At 404, a resource management unit, such as an SoC, obtains theconfiguration state of the operating system and stores it in a database(e.g., memory) associated with the resource management unit. Forexample, the resource management unit 102 described above obtains theconfiguration state by communicating with the processor and memory usinglow-latency communication and read/write transactions, either by way ofthe resource management unit being implemented on a same integratedcircuit die as the processor and its memory, or by using a high-speedinterface bus and data link. The resource management unit may also havea direct memory access (DMA) channel to the memory for transferring datato/from memory without passing it through the processor in the computingsystem.

At 406, the resource management unit identifies a status of a resourcein the computing system based on the operating system configurationstate stored in the database, and identifies a task to be performed thatis associated with the resource. For example, a status of a processresource in the process run queue may be identified as a process that isnext up for execution time on the processor, and that a memory resourceof some number of bytes is needed for the process to execute. As anotherexample, a status of a process resource in the process wait queue may beidentified as one that is waiting for a resource-related event to occur.An example event may be that the process needs a virtual file system(VFS) inode describing a directory in the file system, but that inodemay not be in the cache. Because of this, the process must wait for thatinode to be fetched from the physical media containing the file systembefore it can continue executing.

At 408, the resource management unit processes the task associated withthe status of the resource to alleviate the processor from performingthat task and to improve the performance of the computing system. Forexample, in the context described above (that of a task needing a memoryresource of some number of bytes of memory), the resource managementunit may execute the task of making that memory resource available, suchas by swapping out memory, so that sufficient memory is available whenthe process is actually executed again on the processor. As anotherexample, in the context described above regarding the wait queue waitingfor an inode to be fetched, the resource management unit may execute thetask to fetch the inode in advance of when the operating system andprocessor may be able to do it. This allows processes to avoid waitingto execute relative to if they had waited for the processor (not theresource management unit device's processor) to fetch the inode. Otherexamples include the resource management unit modifying processingpriority or performance factors for a specific process, addressing asecurity aspect of the computing system relative to a particularprocess, and processing other overhead management activities of thecomputing system.

Referring now to FIG. 5, example method 500 depicts additional detailsfor capturing operating system configuration states for offloading tasksto a resource management unit in a computing system. At 502, anoperating system stored in a memory executes on a processor in acomputing system. At 504, during execution of operating systeminstructions, the operating system posts a resource transaction event tomemory indicative of a resource event occurring and a new configurationstate of the operating system. As an example, an abstraction layer ofthe operating system software posts resource transaction event dataindicative of, for example, a process execution status, resource usageand scheduling, memory usage and mapping, hypervisor status,virtual-machine status, and/or any other transaction event that theoperating system is managing for the computing system.

At 506, a resource management unit communicates with the processor andmemory via a low-latency communication data link. Such low-latencycommunication data link may be a high-speed bus (e.g., PCIe) or viacache if the resource management unit is implemented on a sameintegrated circuit die as the processor. At 508 the resource managementunit obtains (e.g., captures) the configuration state of the operatingsystem and stores it to a database associated with the resourcemanagement unit. Note that after a transaction event is posted 504, areturn execution flow arrow 514 in the diagram illustrates that theoperating system continues executing on the processor 502, even whilethe resource management unit communicates 506 with the memory andprocessor. This allows the operating system to continue performing itsoperations, even while the resource management unit is performing itsfunctions 508, 510, 512, for overall improved system performance.

At 510, the resource management unit identifies a status of a resourcefrom the database based on the configuration state of the operatingsystem. For example, a status of a resource may be identified as aprocess that needs additional time to execute, or a process that willneed to access certain I/O resources that need to be retrieved fromstorage, or a process that may pose a security issue if executed, or aprocess or system that may benefit from modifying a clock rate/signalfrequency for a clocked component.

At 512, the resource management unit processes a task associated withthe status of the resource. For example, memory is swapped in advance sothe process waiting next in queue has sufficient memory available whenit begins to execute on the processor as described above, or a resourceis fetched as described above, or additional memory is allocated for theprocess waiting next in queue, or a potential security issue is resolvedconcerning a process, or a component signal frequency is adjusted tomeet processing demands. This awareness of a resource status enables theresource management unit to act on a task in advance of when theprocessor or operating system may eventually perform the task.

After the task is processed for the resource at 512, execution controlreturns, at 516, to allow the resource management unit to identify 510 astatus of a next resource from the database as needed, and processanother task 512 that is associated with that next resource. Thisprocessing is repeated as needed for resources identified in thedatabase. As this resource status identification 510 and task processing512 is performed by the resource management unit, the operating systemcontinues executing 502 and posting resource transaction events 504, andthe resource management unit continues communicating 506 with theprocessor and memory and capturing 508 a configuration state of theoperating system and storing it in the database. This example method ofcapturing operating system configuration states for offloading tasksfrom a processor in a computing system to a resource management unitprovides overall improved computing system performance.

FIG. 6 is a block diagram illustrating an example OS configuration state114 in a memory 108 of a computing system 100 as captured by a resourcemanagement unit 102 into a memory 104 and a database 116. Similar to thediscussion with respect to FIGS. 1-3, the computing system 100 generallyincludes the resource management unit 102, the memory 108, the operatingsystem 110, and the main processor 106. This example depicts operationalstatus information in the memory 108 for exemplary resources asindicative of the OS configuration state 114 at a time that a resourcetransaction event is detected (e.g., the resource transaction event132). In this example, OS configuration state 114 also depicts a processcontrol block 142 representative of a status of an example process inthe process run queue or wait queue as described above in reference toFIG. 1. Although only a single process control block is depicted, aprocess control block exists for each process in the process run queueand wait queue. Upon detecting the resource transaction event 132, theOS configuration state 114 is copied 602 (pushed or pulled) into the OSconfiguration state database 116 on the resource management unit 102.Although the diagram illustrates an example OS configuration stateidentifying a number of example resources, other operating systemconfiguration state resources, resource references, or status indicatorsmay similarly be referenced, identified, and captured by the resourcemanagement unit 102 into the database 116 in coordination with the OSconfiguration state manager 112.

With the database 116 having the OS configuration state 114, theresource management unit 102 may then process a task associated with astatus of any given resource identified in the database to improve theperformance of the computing system. For example, the resourcemanagement unit 102 may increase processing priority or performancecriteria for a specific process, or address a security aspect of thecomputing system relative to a particular process, or process anoverhead management activity of the computing system, or modify a signalfrequency of a clocked component. An example of processing an overheadmanagement activity, such as memory allocation or data fetch, isdescribed above in reference to FIG. 4 and further below in reference toFIG. 9. Having the resource management unit process each of these tasksresults in improved overall system performance and may also improve auser's perception of responsive processing in the computing systembecause the processor 106 can focus on user perceivable activities orother needed activities while the resource management unit 102 performsthe overhead system management work.

Dynamically Scaling Clock Rates with a Resource Management Unit

FIG. 7 is a block diagram illustrating the example computing system 100configured for capturing operating system configuration states by aresource management unit for dynamically scaling clock rates.Dynamically scaling clock rates or clock frequency (used interchangeablyherein) of clocked components in a computing system achieves benefitsincluding performance boost, power optimizations, thermal dynamicconstraints, and reduced processing time. Enabling a resource managementunit, rather than a CPU, to dynamically scale clock rates in the systemresponsive to operating system configuration states, enablesmore-responsive and relevant scaling to active events, and avoids theCPU wasting resources on scaling tasks so that it may address othercomputing system operations.

The operating system 110 executes on the processor 106 from the memory108, and upon detecting an OS transaction event 132, the OSconfiguration state 114 is captured 602 by the OS configuration statemanager 112 of the resource management unit 102 and stored into the OSconfiguration state database 116 of the memory 104. For simplicity anddrawing space limitations, only two example operating system resourcesare shown in the OS configuration state 114 and the database 116, aprocess run queue and a process wait queue, although other OSconfiguration state resources, status indicators, or data may similarlybe represented, referenced, identified, and captured by the resourcemanagement unit 102 into the database 116.

With the process run queue and process wait queue resources representedin the database 116, the resource management unit resource statusmanager 118 may then identify the status of a specific resource 116 inthose queues and process a task 120 associated with the specificresource to improve the performance of the computing system. In thisexample, the resource status manager 118 identifies the status of aprocess resource from the run queue in the database 116 that indicatesit requires or would benefit from modifying the clock rate for a clockedcomponent in the computing system. The benefits include to maintain orimprove performance of the process, overall system performance, powerusage, or thermal dynamics of the computing system 100. In one example,the status of the process resource is identified by referencing theprocess control block. Factors in the process control block consideredmay include the process state, scheduling information, memory managementdata, and accounting data that indicates significant processing time isneeded or consumed or that significant memory is needed. By knowing thestatus of the process, such as when it is going to execute, theresources it needs, and the status of other resources in the computingsystem, the resource management unit may dynamically scale clock ratesaccordingly. Modifying the clock rate may include modifying aperformance of the processor or access speed of the memory to addressload operating conditions, performance, power consumption, thermaldynamics in the computing system, or combinations thereof.

With the captured OS configuration state available 116 that identifiesthe status of the process, and optionally with other process relatedmetrics available, the resource management unit 102 can identifyprocessing needs and clock-rate modification benefits in advance of whatthe operating system 110 may actually detect and execute on theprocessor 106. For example, the OS configuration state, along withassociated process metrics or a detected or assigned process scorerepresenting process metrics, can show that (i) the identified processneeds more memory resources than normal, (ii) the process requiresprocessor intensive activity, (iii) the process may work with reducedmemory resources or reduced processor activity, (iv) a particular corein the processor 106 or a memory bank in the memory 108 may be powereddown (e.g., clock rate terminated) for a short time, or (v) a hypervisoror virtual machine requires increased or reduced processor activity ormemory usage for improved overall system performance.

Where it is determined by the resource status manager 118 that a clockrate of a clocked component in the computing system, such as theprocessor 106 or the memory 108, may be modified to improve aspects ofthe process or the computing system 100, then the resource task manager120 initiates the task of modifying the clock rate for the relevantclocked component. In this depicted example, based on informationidentified about a process in the OS configuration state database 116,the resource task manager 120 may modify a clock rate 702 for a clock704 which modifies the clock rate signal 706 to the memory 108.Similarly, in this depicted example, the resource task manager 120 maymodify the clock rate 702 for a clock 708 which modifies the clock ratesignal 710 to the processor 106. The resource task manager 120 maysimilarly modify the clock rate 702 to any number of other clocks in thesystem 100 to modify the clock rate signal of other respective clockedcomponents not shown in this example (e.g., a graphics processing unit(GPU), MMU, bus, specific memory bank).

To determine whether a process or the overall system may benefit frommodifying the clock rate, any number of factors relating to the process,its process control block, and the OS configuration state 114 may beconsidered including, for example, memory usage, memory need,scheduling, process run queue, process wait queue, process prioritydata, process run-time remaining data, process scheduling data,hypervisor status, virtual-machine status, or combinations thereof.Alternatively, or in combination, processing metrics associated with aprocess (process metrics) may be considered that are indicative ofresources used and system metrics associated with execution of theprocess. Process metrics may be captured, assigned a score, and storedin the database 116, or the score may be detected or obtained if it waspreviously assigned to the process. Process metrics may be captured andobtained by monitoring the process during execution on the processor 106or, if available, retrieved from the database 116 or a storage resource712 external to the computing system 100 and accessible viacommunication manager 122 and the network 126.

Process metrics that reflect resources used and related processing datamay be obtained by using an operating system analysis tool, such as aLinux operating system event-oriented observability tool, e.g., “perf,”This allows for tracking performance counters, events, trace points,tasks, workload, control-flow, cache misses, page faults, and otherprofiling aspects of the operating system. Metrics of the process thatare captured using an observability or profiling tool, or obtained fromthe external storage resource 712, are maintained in the database 116for the resource status manager 118 to reference in determining whethermodifying a clock rate of a component may be advantageous for theprocess or system overall. Modifying the clock rate based on processmetrics may be advantageous in any number of events including, forexample, increasing the clock rate for the memory 108 if the processscore or metrics indicate that the process requires heavy memory usage,or increasing the clock rate for the processor 106 if the process scoreor metrics indicate that the process requires heavy processing, orreducing the clock rate for the processor to reduce thermal issues ifthe process score or metrics indicate heavy processing that createsincreased thermal issues.

Because the process score represents the processing metrics associatedwith the process, it enables the resource status manager 118 to quicklyand easily identify whether the process or the system would benefit frommodifying a clock rate of a clocked component. The score also enablesthe resource status manager 118 to easily compare the process withscores of other processes in the system. A score may be obtained fromthe external storage resource 712 if the process is one that has beenpreviously associated with a score. For example, a process thatrepresents a game played by users on a computing device may be assigneda score relative to its known processing metrics as used in othercomputing devices or systems. That score may then be stored in theexternal storage resource 712 as associated with that particular processand leveraged by the resource management unit 102 to quickly and easilydetermine benefits of modifying clock rates for the process in thecomputing system 100.

The resource task manager 118 may also detect other scores associatedwith other process statuses stored in the OS configuration statedatabase 116, or assign other scores to those other processes based onprocessing metrics detected, or obtain other scores of other processesfrom the storage resource 712, all representative of processing metricsassociated with those other processes and resources used by thoseprocesses. The resource task manager may then compare the process scoreto the scores of the other processes to determine if, when, and how tomodify clock rates for clocked components in the computing system 100for improved system performance.

For example, the process score may be compared with respect to a scoreof another process, or to a combination of scores of multiple otherprocesses in the process run queue, and in an event that the score ofthe other process or a combined score of the multiple other processesmeets a given threshold indicative for modifying the clock rate of thecomponent, then the clock rate of that component may be modified. As oneexample, if the process score is weighted very heavy on processor usage,and there are no other process scores in the process run queue that areweighted processor heavy, then the resource task manager 118 may notneed to modify the clock rate for the process. On the other hand, ifthere are other process scores that are weighted processor heavy in theprocess run queue, then the resource task manager 118 may increase theclock rate for the process relative to the processor 106, the memory108, or other clocked component.

FIG. 8 illustrates an example method 800 for capturing operating systemconfiguration states by a resource management unit for dynamicallyscaling clock rates. At 802, the resource management unit captures aconfiguration state of the operating system in memory that is executingon the processor in the computing system, and stores the configurationstate to a database associated with the resource management unit. At804, the resource management unit identifies from the database a statusof a process resource in the computing system based on the configurationstate of the operating system. In this example for dynamically scalingclock rates, the process may be a process in a run queue waiting toexecute on the processor, or a process in the wait queue that haspartially executed but is paused and waiting for an event to occurbefore beginning to execute again.

The resource management unit examines the process status to determinewhether the process or the computing system would benefit from modifyinga clock rate of a clocked component in the computing system, such as theprocessor or memory, to maintain or improve performance of the process,overall system performance, power consumption, or thermal dynamics ofthe computing system. For example, the resource management unit examinesthe process control blocks of processes in the run queue or wait queue.If a process state, scheduling information, memory management data,and/or accounting data indicate significant processing time still neededor consumed, or significant memory needed, then the processor clock rateor memory clock rate may be increased by the resource management unit toaddress the need. Another example, at 806, is for the resourcemanagement unit to detect whether a process score is associated with theprocess. The process score represents overall processing metricsassociated with the process, and resources used by the process in thecomputing system and operating system, or in another computing systemand operating system external to the computing system with the resourcemanagement unit. The process score enables the resource management unitto easily identify whether the process or the system would benefit frommodifying a clock rate of a clocked component.

If a process score is not detected 806 in association with the process,then a process score may be obtained 808 from an operating systemprofiling tool or an external storage resource. While the process isexecuting in the computing system the process score may be calculated orobtained using standard operating system profiling tools known fortracking performance counters, events, trace points, tasks, workload,control-flow, cache misses, page faults, and other profiling aspects ofthe operating system. Alternatively, the process score may be obtainedfrom an external storage resource.

At 810, if the OS configuration state or process score meets athreshold, then the resource management unit modifies the clock rate 812for a clocked component associated with the process or otherwisebeneficial to the computing system. If the threshold is not met, thenexecution control returns 814 for the resource management unit toidentify 804 a status of another process resource in the computingsystem.

To determine whether an OS configuration state meets the threshold 810for modifying the clock rate, factors associated with the process statusare considered including, for example, memory usage, memory need,scheduling, process run queue, process wait queue, process prioritydata, process run-time remaining data, process scheduling data,hypervisor status, virtual machine status, or combinations thereof. Onthe other hand, the process score allows the resource management unit toeasily compare it to a threshold score 810, or to compare it with scoresof other processes in the system to determine if an overall thresholdscore is met 810. Scores of other processes in the system may beobtained or calculated from a profiling tool while the other processesexecute in the computing system, or from an external storage resource ifthose other processes have been previously associated with a score. Ifthe OS configuration state and/or process score meets the threshold 810,then the resource management unit modifies the clock rate 812 forrespective clocked components in the computing system, and executioncontrol returns 816 to identify 804 a status of another process and acton it.

Modifying the clock rate based on the operating system configurationstate, process status, and metrics may be advantageous in any number ofevents. For example, increasing the clock rate for memory may occur ifthe metrics suggest that the process requires heavy memory usage, orincreasing the clock rate for the processor, or a hypervisor or virtualmachine may occur if the metrics suggest that any requires heavyprocessing. On the other hand, reducing the clock rate for the processormay occur to reduce thermal dynamics if the metrics suggest heavyprocessing that typically creates increased thermal issues, or eventerminating a clock rate briefly may occur in certain components if themetrics suggest no activity in those components.

Offloading Memory Management to a Resource Management Unit

FIG. 9 is a block diagram illustrating an example computing system 100configured with a resource management unit 102 for capturing operatingsystem configuration states and managing memory swapping. The operatingsystem 110 executes on the processor 106 from the memory 108. Upondetecting an OS transaction event 132, the OS configuration state 114 iscaptured 602 by the OS configuration state manager 112 of the resourcemanagement unit 102 and stored into the OS configuration state database116 of the memory 104. For simplicity of discussion and drawinglimitations, only two example operating system resources are shown inthe database 116, a process run queue and a process wait queue, althoughother operating system configuration state resources, status indicators,or data may similarly be represented, referenced, identified, andcaptured by the resource management unit 102 into the database 116.

With the process run queue and process wait queue resources representedin the database 116, in this example the resource management unitresource status manager 118 identifies a process from the run queue inthe database 116 that requires a swap of memory resources 902 associatedwith the process to maintain or improve overall system performance. Theprocess status and resources associated with the process, or relative tothe process, such as identified in the process control block, areidentified from the OS configuration state 114 of the operating system110 as stored in the database 116 by considering any number of aspects.For example, aspects may include memory usage, memory need, secondarymemory usage, scheduling, process run queue, process wait queue, processpriority data, process run-time remaining data, process scheduling data,status of a hypervisor or virtual machine, or combinations thereof.

The term memory swapping may refer to copying an entire process addressspace out to a swap device, such as the secondary storage 124, or back,as a single event. And the term paging may refer to copying, in or out,one or more same-size blocks of the address space, at a much finergrain, such as 4K bytes per block, referred to as a page-size. However,for simplicity of discussion in this disclosure, paging and swappingwill be used interchangeably to reference the copying of memory contentto or from the secondary storage 124.

With the captured OS configuration state available in the database 116,the resource management unit 102 can identify memory swappingrequirements for a process in advance of what the operating system willdetect and execute on the processor 106, thus avoiding memory pagefaults and improving computing system performance. For example, the OSconfiguration state can show that the identified process requires morememory resources to execute than what is currently available in thememory 108, or the process recently completed execution and doesn'trequire the memory resources. The resource status manager 118 reviewsthe process in the database 116 to see if it is a good candidate forswapping, e.g., if it has pages that can be swapped in, or discardedfrom, memory, considering factors such as aging, whether or not the pageis locked in memory, or whether the page is shared in memory.

When the resource status manager 118 determines that the processrequires memory content 902 to be swapped in, or may be swapped out, theresource task manager 120 executes the memory swap 904 between thememory 108 and the secondary storage 124. If the process needs morememory to execute than what is available in the memory 108, then theresource management unit 102 may move other memory content out to thesecondary storage 124 that is not needed for execution at the currenttime, and the resource management unit swaps in content from thesecondary storage 124 that is needed for the process to execute. On theother hand, if the process has completed execution and doesn't need touse the memory content 902, then the resource management unit 102 maymove the memory content 902 out to the secondary storage 124 to free upthe memory 108.

In another example, the memory content 902 is swapped between the memory108 and the secondary storage 124 using a variant size of the memorycontent without a page-size calculation or page-size processing of thecontent. For example, rather than using a standard set page-size (e.g.,1K, 2K or 4K bytes) to swap the memory content 902, thereby requiringmultiple processing tasks of swapping the multiple pages, andpotentially using memory less efficiently, the resource management unit102 may swap the memory content 902 out to the secondary storage 124 ina specific amount needed, either some or all of the memory content 902,or swap it into the memory 108 in the specific amount needed, in onedata-stream swap. For example, if the size of memory that needs swappingis 1.5K, then the resource management unit 102 swaps 1.5K. Thus, thereis no need to process the swap using a traditional page-size calculationor multi-staged page-processing activity to swap some or all of thememory content 902.

This memory management and swapping can be performed because theresource management unit has an understanding of the OS configurationstate 116 and, for example, since both wait queues and schedulingpriorities are known, the resource management unit knows what memoryeach process will use, what memory is free, how much memory is needed tobe swapped, how much memory will be needed by a next process in the runqueue to execute, and other factors that guide usage of the memory forimproved performance in the computing system. The resource managementunit 102 can, using its own direct memory access (DMA) and withoutpausing the processor 106, pre-swap pages for each process before itruns, in the order the process will consume those pages (e.g., usingstack and heap pointers for predicting this) and in case there isinsufficient memory 108 for those pages. The resource management unitalso knows the last process that was executed on the processor 106, andwhich has the most time left until it is back to a running state, so theresource management unit can evict that last process pages to make moreroom in the memory 108 for other processing needs.

Similarly, in the context of a hypervisor 136 or virtual machine 138running in the computing system 100, this memory management processingby the resource management unit 102 for the hypervisor and virtualmachine improves their effectiveness, e.g., the hypervisor swapping outor migrating virtual machines. The resource management unit knows whichvirtual machine will run the latest, and which will be scheduled next,so the resource management unit can fetch the virtual machine to thememory 108 when needed and swap it back to secondary storage after it isdone executing, making the hypervisor more effective.

FIG. 10 illustrates an example method 1000 for capturing operatingsystem configuration states by a resource management unit in a computingsystem for managing memory swapping. At 1002, the resource managementunit captures a configuration state of the operating system executing onthe processor in the computing system, and stores the configurationstate to a database (e.g., memory) associated with the resourcemanagement unit. At 1004, the resource management unit identifies fromthe database a status of a process resource in the computing system, asmay be referenced in the process control block, based on theconfiguration state of the operating system. As an example, the processmay be a process in a run queue but waiting to execute on the processor,or a process that has partially executed but is paused and waiting inthe wait queue for an event to occur before beginning to execute again.

In this example, the resource management unit identifies a process fromthe run queue in the database as requiring to swap memory resources tomaintain process execution or improve system performance. The status ofthe process, and resources associated with the process or relevant tothe process, are identified from the configuration state of theoperating system by considering factors such as its memory usage, memoryneed, secondary memory usage, scheduling, process run queue, processwait queue, process priority data, process run-time remaining data,process scheduling data, hypervisor or virtual machine activity, orcombinations thereof.

At 1006, if it is determined that a memory swap is not required, thenexecution control returns 1012 to identify another process 1004. If isdetermined 1006 that the process requires memory swapped based on thecaptured operating system configuration state, then the resourcemanagement unit determines a memory swap size 1008. In this example, thememory swap size is based on the variant size of the content to beswapped in the memory for improved system performance and efficientmemory usage. Given the captured operating system configuration state,the resource management unit knows the details of the process and othersystem activities so that it can perform the memory swap based on thevariant size of the content, rather than having to perform standard setpage-size transfers of the content.

At 1010, the memory content is swapped to or from a secondary storageusing, in this example, a swap size based on the variant size of thememory content without using a set page-size limitation. For example,the resource management unit may swap the memory content out tosecondary storage, or swap it into the memory from secondary storage, inone data-stream swap using the actual size of the memory content, ratherthan a set page-size, thereby avoiding multiple processing tasks ofswapping multiple pages. After the memory content is swapped 1010,execution control returns 1014 to identify a status of another process1004.

While the resource management unit is processing all these functions ofcapturing the operating system configuration state 1002, identifying aprocess that may require a memory swap 1004, determining whether amemory swap is required 1006, determining the memory swap size 1008, andthen actually swapping the memory content 1010, the operating systemseparately and in parallel continues executing its operations on theprocessor.

Managing Malware and Vulnerabilities with a Resource Management Unit

FIG. 11 is a block diagram illustrating an example computing system 100configured to capture operating system configuration states with aresource management unit 102 for detecting and managing malware andsoftware vulnerabilities. The operating system 110 is executing on theprocessor 106 from the memory 108, and upon detecting an operatingsystem transaction event 132, the OS configuration state 114 is captured602 by the OS configuration state manager 112 of the resource managementunit 102 and stored into the OS configuration state database 116 of thememory 104. For simplicity of discussion and drawing space limitations,only two example operating system resources are shown in the database116, a process run queue and a process wait queue, although otheroperating system configuration state resources, data, or statusindicators 114 may similarly be represented, referenced, identified, andcaptured by the resource management unit 102 into the database 116.

With the process run queue and process wait queue resources representedin the database 116, the resource management unit may then identify thestatus of a resource 118 and process a task 120 associated with theresource to improve the performance of the computing system. In thisexample, the resource management unit resource status manager 118identifies a first process from the run queue in the database 116 asready to be executed (e.g., by referencing the process control block).Prior to execution of the first process, a fingerprint of the firstprocess is identified (e.g., generated) 1102 by the resource taskmanager 120 to subsequently compare to a plurality of fingerprints offlagged processes 1104 stored in the memory 104. In other aspects, thefingerprint of the first process is identified at multiple points intime, such as before, during, and/or immediately after execution, tocapture a potential rolling (e.g., changing) fingerprint of the process.

For this disclosure, a fingerprint represents one or more aspects,characteristics, schemes, traits, or perspectives that identify theprocess or its binary or source files. For example, the fingerprint mayrelate to, or be generated from, (i) the binary program file of theprocess, (ii) the source program file of the process, (iii) aperspective of the process in memory while the process executes (e.g.,as the process code may dynamically morph in memory while executing,including rolling or scattered execution changes in memory such as froma code segment to a data segment), and/or (iv) a perspective of theprocess in memory, or its binary file, or its source file, or somecombination thereof, as generated by a machine learning algorithm.Accordingly, a single process may have multiple fingerprints, and themultiple fingerprints may be linked for association purposes.

The fingerprint of the first process may be identified by executing ahash function on the first process (e.g., by executing a hash functionon the binary program file or source program file of the first process,or on code or data of the process as it exists in memory for executionby the processor). For example, a rolling hash function may be appliedwhere the process data is hashed in a window that moves through thedata, or a Rabin fingerprinting scheme may be applied using polynomials.The fingerprint may also be identified by passing the first processthough a search filter, such as a regular expression (e.g., regex orregexp) engine. This may be accomplished by applying the search filterto the (i) binary program file of the process, (ii) source program fileof the process, (iii) code or data of the process as it exists inmemory, and/or (iv) data, memory or devices the process is accessing.Such regular expression functionality may be applied recursively, oriteratively, using varying parameters to progressively narrow the scopeand results. The fingerprint generation method simply aligns with thefingerprint generation method of the plurality of fingerprints offlagged processes 1104 stored in the memory 104 of the resourcemanagement unit so that an accurate comparison may be made.

The plurality of fingerprints of flagged processes 1104 are indicativeof processes, executable files, programs, applications, operatingsystems, or other software that include executable instructions or arebinary program files that have a known vulnerability or have beenidentified as malware. Examples of malware may be in the form of avirus, trojan, worm, adware spyware, or ransomware, or any software thatis specifically designed to disrupt, damage, or gain unauthorized accessto or control of the computing system, or to steal or corrupt data. Avulnerability is any weakness in the software or in the operating systemthat may be exploited to disrupt, damage, or gain unauthorized access toor control of the computing system, or compromise or cause unintendedbehavior of the computing system.

The fingerprints of the flagged processes 1104 may be obtainedperiodically (meaning occasionally or continuously as system parametersallow) by the resource task manager 120 from an external storage 1106through the resource management unit communication manager 122 and thenetwork 126. The external storage 1106 may be a database on a localnetwork external to the computing system, or a database located in aremote computing environment, such as a cloud computing environment ormulti-cloud environment, accessed via the Internet. The external storage1106 maintains a list of fingerprints of known malware and vulnerablesoftware. The resource management unit accesses the external storage1106 periodically to update its own memory of fingerprints of flaggedprocesses 1104.

The resource management unit 102 compares the fingerprint of the firstprocess 1102 to the fingerprints of the flagged processes 1104 stored inthe memory 104 of the resource management unit. Alternatively, or incombination with comparing to the fingerprints of the flagged processes1104 stored in the memory 104, the resource management unit may comparethe fingerprint of the first process to the fingerprints of the flaggedprocesses as stored in the external storage 1106.

If there is not a match of the fingerprint of the first process 1102 toany of the fingerprints of the flagged processes 1104, then no action istaken, and the resource management unit 102 and the processor 106continue executing their normal commands and functions. However, ifthere is a match of the fingerprint of the first process 1102 to atleast one of the fingerprints of the flagged processes 1104, then thefirst process is recognized as malware or a vulnerable process, as thecase may be, and the resource task manager 120 takes action to protectthe computing system from unwanted effects of the first process. Suchaction may include any number of separately actionable or coordinatedevents between the resource management unit, the processor, and/or theoperating system to protect the computing system. For example, suchaction may include notifying a user of the computing system, prohibitingexecution of the first process, suspending scheduling of the firstprocess, limiting execution of the first process, stopping execution ofthe first process, archiving the first process in a secure vault,removing the first process completely, stopping certain processing inthe computing system, or combinations thereof.

While the resource management unit is processing all these describedfunctions of capturing the OS configuration state 114 and managingmalware and vulnerabilities, the operating system 110 separately and inparallel continues executing its operations on the processor 106. Thisleaves the processor and operating system unburdened by the activitiesof the resource management unit unless a vulnerable process or malwareis detected and acted on.

FIG. 12 illustrates an example method 1200 for a resource managementunit, such as a SoC, to capture operating system configuration states ofan operating system executing on a processor in a computing system, andto detect and manage a vulnerable process or malware in the computingsystem. At 1202, a plurality of fingerprints of flagged processes arestored to a memory of the resource management unit. The flaggedprocesses are indicative of processes, executable files, programs,applications, operating systems, or other software that includeexecutable instructions that have a known vulnerability or have beenidentified as malware. The plurality of fingerprints of the flaggedprocesses may be obtained periodically from an external storage whichmaintains a list of fingerprints of known malware and vulnerabilities.The resource management unit accesses the external storage periodicallyto update its own memory of fingerprints of flagged processes.

At 1204, the resource management unit obtains a configuration state ofthe operating system executing on the main processor in the computingsystem, and stores the configuration state to a database associated withthe resource management unit. At 1206, the resource management unitidentifies from the database a status of a first process resource in thecomputing system based on the configuration state of the operatingsystem. As an example, the first process may be a process in a run queuebut waiting to execute on the processor, or a process that has partiallyexecuted but is paused and waiting in the wait queue for an event tooccur before beginning to execute again.

At 1208, the resource management unit identifies a fingerprint of thefirst process. The fingerprint may be identified, for example, byexecuting a hash function on the first process to generate afingerprint, or by passing the first process through a search filter, orsome combination thereof. Multiple fingerprints of the first process mayalso be identified (e.g., generated), at different points in timerelative to execution, and linked for association with the process.

At 1210, the resource management unit compares the fingerprint of thefirst process to the fingerprints of the flagged processes stored in thememory of the resource management unit. Alternatively, or in combinationwith comparing to the fingerprints of the flagged processes stored inthe memory, the resource management unit may compare the fingerprint ofthe first process to the fingerprints of the flagged processes as storedin the external storage.

If there is not a match 1212 of the fingerprint of the first process toany of the fingerprints of the flagged processes, then execution controlreturns 1216 for the resource management unit to repeat the steps ofidentifying another process 1206, identifying a fingerprint 1208, andcomparing the fingerprint 1210 to fingerprints of flagged processes. Ifthere is a match 1212 of the fingerprint of the first process to one ofthe fingerprints of the flagged processes, then the first process isrecognized as malware or a vulnerable process, as the case may be, andthe resource management unit takes action 1214 to protect the computingsystem from unwanted effects of the first process. Such action mayinclude any number of actions as described above in reference to FIG.11.

Notably, while the resource management unit is processing all thesefunctions depicted in the method 1200, and also while the resourcemanagement unit repeats processing these functions against differentprocess resources identified in the computing system based on capturingthe configuration state of the operating system, the operating systemseparately and in parallel continues executing its operations on theprocessor in the computing system for overall improved computing systemperformance.

While this disclosure has been described with respect to exampleembodiments outlined above, it is evident that alternatives,modifications, and variations will be apparent to those skilled in theart. Accordingly, the described and depicted embodiments of the presentdisclosure are intended to be illustrative, not limiting, and thesubject of the appended claims is not necessarily limited to thespecific features or methods described in this disclosure.

EXAMPLES

In the following paragraphs, some examples are described.

Example 1: A method of managing a computing system (100; 300), themethod including: capturing (112; 404; 508), by a resource managementunit (102) and into a first memory (104), a configuration state (114) ofan operating system (110) in a second memory (108), the operating system(110) executing on a processor (106) of the computing system;identifying (118; 406; 1004), by the resource management unit (102), astatus of a process (116) in the computing system (100; 300) based onthe configuration state (114) of the operating system (110), the statusof the process indicative of requiring to swap a memory resource in thecomputing system; and responsive to identifying the status of theprocess indicative of requiring to swap the memory resource, swapping,by the resource management unit (102), the memory resource (120; 904;1010) effective to alleviate the processor (106) from swapping thememory resource.

Example 2: The method of example 1 wherein the status of the processindicative of requiring to swap the memory resource is indicative of theprocess needing the memory resource to execute on the processor, or theprocess completed execution and not needing the memory resource.

Example 3: The method of any preceding example wherein swapping thememory resource includes swapping a content of the memory resourcebetween the second memory and a secondary storage.

Example 4: The method of any preceding example wherein swapping thememory resource includes swapping a content of the memory resource usinga variant size of the content of the memory resource without a page-sizeor block-size calculation of the content.

Example 5: The method of any preceding example wherein swapping thememory resource includes swapping a content of the memory resource froma secondary storage into the second memory before execution of theprocess by the processor for the process to use the content in thesecond memory during execution of the process by the processor.

Example 6: The method of any preceding example wherein swapping thememory resource includes swapping a content of the memory resource fromthe second memory to a secondary storage after execution of the processby the processor for a second process to use the second memory uponexecution of the second process by the processor.

Example 7: The method of any preceding example further including theresource management unit communicating with the processor or the secondmemory for capturing the configuration state of the operating systemusing a low-latency communication data link or a high-speed interfacebus, or by being integrated with a same integrated circuit die as theprocessor.

Example 8: The method of any preceding example wherein capturing theconfiguration state of the operating system includes an abstractionlayer of instructions coordinating with the operating system as executedby the processor for detecting a resource transaction event associatedwith the operating system and pushing the configuration state of theoperating system to the first memory of the resource management unitresponsive to the resource transaction event.

Example 9: The method of any preceding example wherein capturing theconfiguration state of the operating system includes the resourcemanagement unit detecting a resource transaction event associated withthe operating system and pulling the configuration state of theoperating system to the first memory of the resource management unitresponsive to the resource transaction event.

Example 10: The method of any preceding example wherein identifying thestatus of the process includes identifying a memory usage, memory need,secondary storage, scheduling data, process run queue, process waitqueue, process priority data, process run-time remaining, hypervisor,virtual machine, or combinations thereof.

Example 11: The computing system (100; 300) of any of examples 1 to 10including: the processor (106); the resource management unit (102); andthe first or second memory (104; 108) having instructions stored thereonthat, responsive to execution by the processor (106) or the resourcemanagement unit (102), cause the resource management unit (102) toexecute the method of any of examples 1 to 10.

Example 12: The computing system (100; 300) of any of examples 1 to 10including: the processor (106); the resource management unit (102)including a system-on-a-chip, an application-specific integratedcircuit, or an application-specific standard product; and the first orsecond memory (104; 108) having instructions stored thereon that,responsive to execution by the processor (106) or the resourcemanagement unit (102), cause the resource management unit (102) toexecute the method of any of examples 1 to 10.

Example 13: The computing system (100; 300) of any of examples 1 to 10including: a hypervisor (136) or a virtual machine (138); the processor(106); the resource management unit (102); and the first or secondmemory (104; 108) having instructions stored thereon that, responsive toexecution by the processor (106) or the resource management unit (102),cause the resource management unit (102) to execute the method of any ofexamples 1 to 10.

Example 14: The first or second memory (104, 108) of any of examples 1to 10 including instructions that, when executed by the processor (106)or the resource management unit (102), cause the resource managementunit (102) to perform the method of any of examples 1 to 10.

Example 15: The computing system (100; 300) of any of examples 1 to 10,further including means to perform the method of any of examples 1 to10.

Example 16: The method of any of examples 1 to 10 wherein capturing theconfiguration state of the operating system includes obtainingoperational status information of the operating system concerning atleast one of a process run queue, a process wait queue, process prioritydata, process run-time remaining data, resource scheduling data,resource usage data, active device data, memory usage data, memorymapping data, virtual memory tables, storage management data, a statusof the hypervisor, a status of the virtual machine, a status of a guestoperating system in the virtual machine, resources of the computingsystem used by the hypervisor, resources of the computing system used bythe virtual machine, or combinations thereof.

Example 17: The method of any of examples 1 to 10 wherein identifyingthe status of the process in the computing system includes accessing thefirst memory and identifying a status of at least one of a process runqueue, process wait queue, process priority data, process run-timeremaining data, resource scheduling data, active device data, memoryusage data, memory mapping data, virtual memory tables, storagemanagement data, hypervisor, virtual machine, the guest operating systemin the virtual machine, resources of the computing system used by thehypervisor, resources of the computing system used by the virtualmachine, or combinations thereof.

Example 18: The first and second memory (104, 108) of any of examples 1to 9 comprising a shared memory and instructions that, when executed bythe processor (106) or the resource management unit (102), cause theresource management unit (102) to perform the method of any of claims 1to 10.

1. A method of managing a computing system, the method comprising: capturing, by a resource management unit and into a first memory, a configuration state of an operating system in a second memory, the operating system executing on a processor of the computing system; identifying, by the resource management unit, a status of a process in the computing system based on the configuration state of the operating system, the status of the process indicating a requirement to swap a memory resource in the computing system; and responsive to identifying the status of the process indicating the requirement to swap the memory resource, swapping, by the resource management unit, the memory resource effective to alleviate the processor from swapping the memory resource.
 2. The method of claim 1, wherein swapping the memory resource comprises swapping a content of the memory resource between the second memory and a secondary storage.
 3. The method of claim 2, wherein swapping the memory resource comprises swapping the content of the memory resource using a variant size of the content of the memory resource without a page-size calculation of the content.
 4. The method of claim 2, wherein swapping the memory resource comprises swapping the content of the memory resource from the secondary storage into the second memory before execution of the process by the processor, the swapping for the process to use the content in the second memory during execution of the process by the processor.
 5. The method of claim 1, wherein swapping the memory resource comprises swapping a content of the memory resource from the second memory to a secondary storage after execution of the process by the processor for a second process to use the second memory upon execution of the second process by the processor.
 6. The method of claim 1 further comprising the resource management unit communicating with the processor or the second memory for capturing the configuration state of the operating system using a low-latency communication data link or a high-speed interface bus, or by being integrated with a same integrated circuit die as the processor.
 7. The method of claim 1, wherein capturing the configuration state of the operating system comprises an abstraction layer of instructions coordinating with the operating system as executed by the processor for detecting a resource transaction event associated with the operating system and pushing the configuration state of the operating system to the first memory of the resource management unit responsive to the resource transaction event.
 8. The method of claim 1, wherein capturing the configuration state of the operating system comprises the resource management unit detecting a resource transaction event associated with the operating system and pulling the configuration state of the operating system to the first memory of the resource management unit responsive to the resource transaction event.
 9. The method of claim 1, wherein identifying the status of the process comprises identifying a memory usage, memory need, secondary storage, scheduling data, process run queue, process wait queue, process priority data, process run-time remaining, hypervisor, virtual machine, or combinations thereof.
 10. A computing system comprising: a processor; a resource management unit; a first memory; and a second memory having an operating system, the first or second memory having instructions stored thereon that, responsive to execution by the processor or the resource management unit, cause the resource management unit to perform operations comprising: capturing, by the resource management unit and into the first memory, a configuration state of the operating system in the second memory, the operating system executing on the processor of the computing system; identifying, by the resource management unit, a status of a process in the computing system based on the configuration state of the operating system, the status of the process indicating a requirement to swap a memory resource in the computing system; and responsive to identifying the status of the process indicating the requirement to swap the memory resource, swapping, by the resource management unit, the memory resource effective to alleviate the processor from swapping the memory resource.
 11. The computing system of claim 10, wherein the resource management unit includes a system-on-a-chip, an application-specific integrated circuit, or an application-specific standard product.
 12. The computing system of claim 10, wherein swapping the memory resource comprises swapping a content of the memory resource between the second memory and a secondary storage.
 13. The computing system of claim 12, wherein swapping the memory resource comprises swapping the content of the memory resource using a variant size of the content of the memory resource without a page-size calculation of the content.
 14. The computing system of claim 12, wherein swapping the memory resource comprises swapping the content of the memory resource from the secondary storage into the second memory before execution of the process by the processor, the swapping for the process to use the content in the second memory during execution of the process by the processor.
 15. The computing system of claim 10, wherein swapping the memory resource comprises swapping a content of the memory resource from the second memory to a secondary storage after execution of the process by the processor for a second process to use the second memory upon execution of the second process by the processor.
 16. The computing system of claim 10, wherein the operations further comprise the resource management unit communicating with the processor or the second memory for capturing the configuration state of the operating system using a low-latency communication data link or a high-speed interface bus, or by being integrated with a same integrated circuit die as the processor.
 17. The computing system of claim 10, wherein capturing the configuration state of the operating system comprises an abstraction layer of instructions coordinating with the operating system as executed by the processor for detecting a resource transaction event associated with the operating system and pushing the configuration state of the operating system to the first memory of the resource management unit responsive to the resource transaction event.
 18. The computing system of claim 10, wherein capturing the configuration state of the operating system comprises the resource management unit detecting a resource transaction event associated with the operating system and pulling the configuration state of the operating system to the first memory of the resource management unit responsive to the resource transaction event.
 19. The computing system of claim 10, wherein identifying the status of the process comprises identifying a memory usage, memory need, secondary storage, scheduling data, process run queue, process wait queue, process priority data, process run-time remaining, hypervisor, virtual machine, or combinations thereof.
 20. The computing system of claim 10, further comprising a hypervisor or virtual machine, and wherein: capturing, by the resource management unit and in the first memory, the configuration state of the operating system captures the configuration state of the operating system of the hypervisor or the virtual machine. 